Information Processing Method and Apparatus

ABSTRACT

An information processing method includes receiving first request information entered by a user, determining a first task engine for the first request information, where a first slot is set in the first task engine, extracting key information from the first request information based on the first slot, and if the key information fails to be extracted from the first request information based on the first slot, or if the key information is extracted from the first request information based on the first slot, but the extracted key information does not meet a condition, obtaining target key information from a shared parameter list of the user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Patent ApplicationNo. PCT/CN2018/122196, filed on Dec. 19, 2018, which claims priority toChinese Patent Application No. 201810388248.8, filed on Apr. 26, 2018.The disclosures of the aforementioned applications are herebyincorporated by reference in their entireties.

TECHNICAL FIELD

This application relates to the field of computer technologies, and inparticular, to an information processing method and apparatus.

BACKGROUND

With rapid development of the Internet, a human-computer interactionsystem is increasingly widely used. Input of the human-computerinteraction system may be a request such as a weather query, air ticketbooking, encyclopedic knowledge, and a chat. The human-computerinteraction system may feed back, based on a request of a user,information that meets a user requirement. For example, the requestentered by the user may be “weather conditions of Beijing tomorrow”, andthe information fed back by the human-computer interaction system to theuser may be “weather of Beijing tomorrow is sunny to cloudy”.

In some approaches, the human-computer interaction system needs toobtain key information that meets a condition from request informationof the user. If the key information that meets the condition fails to beobtained from the request information of the user, the human-computerinteraction system feeds back, to the user, information indicating thatprocessing fails, and consequently user experience is relatively poorand human-computer interaction efficiency is low.

SUMMARY

This application provides an information processing method andapparatus, to achieve relatively good user experience and relativelyhigh human-computer interaction efficiency.

According to a first aspect, this application provides an informationprocessing method, including receiving first request information enteredby a user, determining a first task engine for the first requestinformation, where a first slot is set in the first task engine,extracting key information from the first request information based onthe first slot, and if the key information fails to be extracted fromthe first request information based on the first slot, or if the keyinformation is extracted from the first request information based on thefirst slot, but the extracted key information does not meet a condition,obtaining target key information from a shared parameter list of theuser, where the shared parameter list includes at least a correspondencebetween a second slot and the target key information, the second slotand the first slot have a same slot type, the second slot is a slot inthe second task engine, and the first task engine is different from thesecond task engine.

In this embodiment of this application, if the key information fails tobe extracted for the first slot, or if the extracted key informationdoes not meet the condition, the target key information is obtained fromthe shared parameter list of the user. Compared with another solution inwhich when the key information fails to be extracted or the extractedkey information does not meet the condition, information indicating thatprocessing fails is fed back such that the user enters a request again,better user experience and higher human-computer interaction efficiencycan be achieved.

In a possible implementation, the shared parameter list includes acorrespondence between the first task engine and one or more taskengines, a correspondence between slots included in any two task enginesthat have a correspondence, and the correspondence between the secondslot and the target key information, where the one or more task enginesinclude the second task engine.

The following manner may be used to obtain the target key informationfrom the shared parameter list of the user determining the second taskengine based on the correspondence between the first task engine and theone or more task engines, determining, based on the correspondencebetween slots and from slots that are included in the second task engineand that are included in the shared parameter list, the second slot thathas a correspondence with the first slot of the first task engine, anddetermining the target key information based on the correspondencebetween the second slot and the target key information.

Optionally, the second task engine is configured for second requestinformation of the user, where the second request information and thefirst request information occur within a preset time, and the secondrequest information and the first request information occur within apreset quantity of dialogue rounds. One round of dialogue may refer to aprocess in which the user enters a piece of request information and ahuman-computer interaction system feeds back a piece of information.

In this embodiment of this application, the second task engine isdetermined with reference to the shared parameter list and an occurrencetime of request information such that the second task engine can belocated accurately, and accuracy of the target key information filled inthe second slot is improved.

In a possible implementation, a correspondence between a second slot andthe target key information is stored in the shared parameter list. Thefollowing manner may be used to obtain the target key information fromthe shared parameter list of the user determining, using a contextparameter of the user, the second task engine that is adjacent to thefirst task engine in terms of time, determining, from slots of thesecond task engine, the second slot having the same type as the firstslot, and determining the target key information based on thecorrespondence between the second slot and the target key information.The second task engine is configured for the second request informationof the user, a slot having the same type as the first slot is set in thesecond task engine, and the adjacency of time means that an occurrencetime of the second request information is adjacent to an occurrence timeof the first request information. In a possible implementation, when thesecond slot having the same type as the first slot is being determined,if there are two or more slots having the same type as the first slottype, the second slot may be selected based on preset priorityinformation.

In this embodiment of this application, only one correspondence isstored in the shared parameter list, that is, a correspondence betweendifferent slots of a task engine and target key information. Comparedwith the foregoing implementation of the shared parameter list (threecorrespondences needs to be stored in the foregoing shared parameterlist), the manner of this application can reduce a data amount ofinformation stored in the shared parameter list, and improve a rate foraccessing the shared parameter list.

In a possible implementation, the shared parameter list is a sharedparameter list exclusively occupied by the second task engine, and theshared parameter list exclusively occupied by the second task engine mayinclude the correspondence between the second slot and the target keyinformation. The following manner may be used to obtain the target keyinformation in the shared parameter list of the user determining thesecond task engine based on a correlation between the first task engineand the second task engine, where the correlation between the first taskengine and the second task engine is greater than a preset threshold,determining, based on the second task engine, the shared parameter listexclusively occupied by the second task engine, searching the sharedparameter list exclusively occupied by the second task engine for a slotthat has the same slot type as the first slot, and using the slot as thesecond slot, and determining the target key information based on thecorrespondence between the second slot and the target key information.

In this embodiment of this application, each task engine of thehuman-computer interaction system maintains one shared parameter list,and a correspondence between a slot of the task engine and target keyinformation is stored in the shared parameter list. Compared with theforegoing two shared parameter lists, where three correspondences aremaintained in one list, and a correspondence between slots of aplurality of task engines and target key information is stored inanother list, using the shared parameter list of this application canfurther reduce the data amount of the information stored in the sharedparameter list, and further improve the rate of accessing the sharedparameter list.

In this embodiment of this application, the key information that doesnot meet the condition includes demonstrative information. In thecorrespondence between the second slot and the target key informationincluded in the shared parameter list, the target key informationcorresponding to the second slot is unique, and the key informationcorresponding to the second slot is updatable.

In a possible implementation, the following manner may be used to updatethe target key information corresponding to the second slot. The manneris as follows receiving third request information entered by the user,where the second task engine is configured for the third requestinformation, extracting, from the third request information, keyinformation corresponding to the second slot of the second task engine,and updating, based on the key information corresponding to the secondslot that is extracted from the third request information, the targetkey information corresponding to the second slot in the correspondencebetween the second slot and the target key information included in theshared parameter list.

In this embodiment of this application, a plurality of slots may be setin the first task engine. The following manner may be used to determinethe first slot in the plurality of slots, and is determining theplurality of slots set in the first task engine, where the plurality ofslots have priority information, and determining the first slot based onthe priority information of the plurality of slots.

In an example of this application, the slot type may be a time, a place,a behavior, a character, or the like.

In a possible implementation, the shared parameter list may be stored ata local end, for example, stored in a memory in the informationprocessing apparatus, or may be obtained from an external storage devicethrough a communications network or an access interface.

According to a second aspect, this application provides an informationprocessing apparatus, used for a terminal device or a server. Theinformation processing apparatus includes a unit or a means configuredto perform steps in the first aspect.

According to a third aspect, this application provides an informationprocessing apparatus, used for a terminal device or a server. Theinformation processing apparatus includes at least one processingelement and at least one storage element. The at least one storageelement is configured to store a program and data, and the at least oneprocessing element is configured to perform the method provided in thefirst aspect of this application.

According to a fourth aspect, this application provides acomputer-readable storage medium. The computer-readable storage mediumstores an instruction, and when the instruction is run on a computer,the computer is enabled to perform the method according to the firstaspect.

According to a fifth aspect, this application provides a computerprogram, where the computer program includes a computer instruction, andwhen the computer instruction is executed by a computer, the computer isenabled to perform the method according to the first aspect.

According to a sixth aspect, this application provides a human-computerinteraction system, including a central control module and a task enginemodule. The central control module is implemented by an informationprocessing apparatus provided in this application, and the engine moduleis configured to implement functions of a first task engine and a secondtask engine. In a possible implementation, the human-computerinteraction system further includes a multi-task parameter sharingmanagement module, and the shared parameter list may be stored in theshared parameter management module.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a human-computer interaction system according to thisapplication.

FIG. 2 is another human-computer interaction system according to thisapplication.

FIG. 3 shows an information processing procedure according to thisapplication.

FIG. 4A shows another information processing procedure according to thisapplication.

FIG. 4B shows another information processing procedure according to thisapplication.

FIG. 5 is a schematic diagram of a shared parameter list according tothis application.

FIG. 6 is another schematic diagram of a shared parameter list accordingto this application.

FIG. 7 is still another schematic diagram of a shared parameter listaccording to this application.

FIG. 8A shows still another information processing procedure accordingto this application.

FIG. 8B shows still another information processing procedure accordingto this application.

FIG. 9 is a structural diagram of a communications apparatus accordingto this application.

FIG. 10 is another structural diagram of a communications apparatusaccording to this application.

DESCRIPTION OF EMBODIMENTS

As shown in FIG. 1, this application provides a human-computerinteraction system. The human-computer interaction system mainlyincludes a central control module and a task engine module. Thehuman-computer interaction system may further include a task statuslibrary module.

The central control module is mainly responsible for distributingsession requests to one or more related task engine modules, and thenperforming summarizing and making a decision based on results returnedby a plurality of task engine modules to obtain a final result.

The task engine module includes a plurality of task engines. Each taskengine is mainly configured to be responsible for a session service in aspecific field, for example, parsing request information entered by auser in order to obtain key information that meets a condition. Forexample, for an air ticket booking task engine, key information thatmeets an air ticket booking task, such as departure place information,destination information, and time information, may be extracted fromrequest information entered by the user.

The task status library module is mainly configured to store anintermediate state of a user session task.

In this application, after the task engine module obtains the keyinformation that meets the condition, the task engine module may executea corresponding task based on the key information, or the centralcontrol module may execute a corresponding task based on the keyinformation, or an intelligent terminal may execute a corresponding taskbased on the key information, or a new module may be developed in thehuman-computer interaction system, and is configured to execute acorresponding task based on the key information. In this application, anentity for executing the corresponding task based on the key informationis not limited.

It should be noted that a function of the human-computer interactionsystem may be implemented by a server, by a terminal device, or jointlyby the server and the terminal device.

Therefore, that the human-computer interaction system mainly includes acentral control module and a task engine module may be understood as,when the function of the human-computer interaction system isimplemented by the server, the server includes the central controlmodule and the task engine module, or when the function of thehuman-computer interaction system is implemented by the terminal device,the terminal device includes the central control module and the taskengine module.

In an example of this application, an example in which “after obtainingthe key information that meets the condition, the task engine modulesends the key information to the central control module, and the centralcontrol module executes the corresponding task” is used to detail aworking process of the entire human-computer interaction system.

The user enters request information to an intelligent terminal, wherethe request information may be voice information, text information, orimage information. The intelligent terminal forwards the requestinformation of the user to the central control module of thehuman-computer interaction system. The central control module forwardsthe request information of the user to one or more task engines in thetask engine module. The task engine may parse the request information,obtain key information that meets a condition, and send the keyinformation that meets the condition to the central control module. Thecentral control module may execute a corresponding task based on the keyinformation fed back by the task engine module. In addition, the taskengine may store a corresponding parsing result in a corresponding taskstatus in the task status library module.

For example, a user A enters a request that “I want to book an airticket from Beijing to Shanghai tomorrow” to the intelligent terminal,and in this case, the intelligent terminal may send the request that“The user A wants to book an air ticket from Beijing to Shanghaitomorrow” to the central control module. The central control module mayfirst determine that the request should be handled by the “air ticketbooking task engine”, and then send the request that “The user A wantsto book an air ticket from Beijing to Shanghai tomorrow” to the airticket booking task engine in the task engine module. The air ticketbooking task engine may parse the request information that “The user Awants to book an air ticket from Beijing to Shanghai tomorrow” to obtainthe following key information that meets a condition {intention=“airticket booking”, time=“tomorrow”, departure place=“Beijing”, anddestination=“Shanghai”}, and then the “air ticket booking task engine”may feed back the key information to the central control module. Thecentral control module may book, for the user A, “an air ticket fromBeijing to Shanghai tomorrow” based on the key information fed back bythe “air ticket booking task engine”, finally generate feedbackinformation of a processing result “the air ticket from Beijing toShanghai tomorrow has been booked for you, and booking informationis * * * *”, and send the feedback information to the intelligentterminal. The intelligent terminal may display the feedback informationto the user using a text, a voice, an image, or the like.

It can be learned from the foregoing analysis that, in thehuman-computer interaction system shown in FIG. 1, when a task requestof the user is being handled, key information that meets a taskexecution condition needs to be obtained such that the task request ofthe user can be handled. For example, for a request of an air ticketbooking task, key information such as “a time, a departure place, and adestination” that meets the air ticket booking task needs to be obtainedsuch that an air ticket can be booked for the user based on the taskrequest of the user. For a request of a weather query task, keyinformation such as “location and time” that meets the weather querytask needs to be obtained in order to query the weather for the user. Ifkey information fails to be extracted from a task request, or if keyinformation can be extracted from a task request, but the extracted keyinformation does not meet a condition, the human-computer interactionsystem feeds back a prompt such as “processing fails, please enterinformation again”, and the user needs to enter request informationagain. Consequently, human-computer interaction efficiency is low. Forexample, if the user first enters request information that “I want tobook an air ticket from Beijing to Shanghai tomorrow”, and then entersrequest information that “How is the weather over there?”, because whenthe request information that “How is the weather over there” is beinghandled, key information such as weather and a place that meet theweather query task fails to be extracted, the human-computer interactionsystem feeds back “Which city do you want to ask about the weather”.Consequently, user experience is poor, and human-computer interactionefficiency is low.

Based on the foregoing scenario, as shown in FIG. 2, this applicationprovides a human-computer interaction system, including at least acentral control module, a task engine module, and a multi-task parametersharing management module. Optionally, the system may further include atask status library module.

For corresponding functions of the central control module, the taskengine module, and the task status library module, refer to recordsshown in FIG. 1. Details are not described herein again.

The multi-task parameter sharing management module may store a sharedparameter list. There may be one shared parameter list, and n taskengines in the human-computer interaction system may share the sharedparameter list. Alternatively, there may be a plurality of sharedparameter lists, and each task engine in the human-computer interactionsystem exclusively occupies one shared parameter list. For example, theentire human-computer interaction system includes the n task engines. Inthis case, the multi-task parameter sharing management module mayinclude n shared parameter lists, and each task engine in the n taskengines exclusively occupies one shared parameter list in the n sharedparameter lists.

Optionally, the multi-task parameter sharing management module mayfurther include a multi-task parameter sharing management unitconfigured to manage the shared parameter list.

In this embodiment of this application, the shared parameter list may begenerated based on a historical dialogue parameter of a user. In thisembodiment of this application, when the task engine module fails toextract key information from request information entered by the user, orwhen the task engine module can extract key information but theextracted key information does not meet a condition, the task enginemodule may obtain target key information that meets the condition fromthe shared parameter list. The user does not need to enter requestinformation repeatedly such that user experience is relatively good, andhuman-computer interaction efficiency is effectively improved.

Based on the human-computer interaction system shown in FIG. 2, thisapplication provides an information processing method. The method may beexecuted by the intelligent terminal shown in FIG. 1 or FIG. 2 or theserver in which the human-computer interaction system shown in FIG. 1 orFIG. 2 is run, where the server may be but is not limited to a cloudserver. In this embodiment of this application, that a server in whichthe human-computer interaction system is run is an execution body isused as an example, as shown in FIG. 3, to detail a procedure of theinformation processing method.

Step S301. The server receives first request information entered by auser.

In this embodiment of this application, the first request informationmay be voice information, text information, image information, or thelike. The user may enter the first request information to an intelligentterminal, and the intelligent terminal may forward the first requestinformation to the server.

Step S302. The server performs intention identification on the receivedfirst request information to determine a first task engine responsiblefor the first request information.

In this embodiment of this application, a central control module in theserver may perform intention identification on the first requestinformation, and determine, based on an intention identification result,the first task engine responsible for the first request information. Forexample, the central control module determines that the intentionidentification result of the first request information is air ticketbooking, and in this case, the central control module may determine thatthe first task engine responsible for the first request information isan air ticket booking task engine.

In this embodiment of this application, different slots (slot) may beset in each task engine, the slot may be a variable, and a value (slotview) of the slot may be key information corresponding to the slot. Inthis embodiment of this application, the slot may also be referred to asan information slot, and the key information corresponding to the slotmay also be referred to as slot information. In this embodiment of thisapplication, that a first slot is set in the first task engine is usedas an example to detail a process of this application. It should benoted that, in this embodiment of this application, terms such as“first” and “second” in the first task engine, the second task engine,the first slot, and the second slot are only used to distinguish betweendescriptions, and shall not be understood as an indication orimplication of relative importance or indication or implication of anorder.

Step S303. The server extracts key information from the first requestinformation based on the first slot.

For example, the first task engine is an “air ticket booking taskengine”, and the first slot is a “departure place slot”. In this case,the server may extract, from the first request information, keyinformation corresponding to the “departure place slot”. For anotherexample, the first slot is a “destination slot”. In this case, theserver may extract, from the first request information, key informationcorresponding to the “destination slot”.

Step S304. If the key information fails to be extracted from the firstrequest information based on the first slot, or if the key informationis extracted from the first request information based on the first slot,but the extracted key information does not meet a condition, the serverobtains target key information from a shared parameter list of the user.

The shared parameter list includes at least a correspondence between thesecond slot and the target key information, the second slot and thefirst slot have a same slot type, and the slot type is a time, alocation, a behavior, a character, or the like. The second slot is aslot in the second task engine, and the first task engine is differentfrom the second task engine. The key information that does not meet thecondition may be demonstrative information, where the demonstrativeinformation may be a demonstrative word extracted from the first requestinformation, and the demonstrative word may be, for example, “this”,“that”, “here”, and “there”.

Step S305. The server executes a corresponding task based on the targetkey information.

It can be learned from the foregoing that, in this embodiment of thisapplication, when the key information fails to be extracted from thefirst request information entered by the user, or when the keyinformation can be extracted, but the extracted key information does notmeet the condition, the server may obtain the target key informationfrom the shared parameter list of the user, and execute thecorresponding task based on the target key information. Compared withthe foregoing solution shown in FIG. 1 in which when the key informationfails to be extracted, or the extracted key information does not meetthe condition, the user is requested to enter request information again,using the solution in this application can achieve better userexperience and higher human-computer interaction efficiency.

In an example of this application, a plurality of slots may be set inthe first task engine, all the slots have a same priority, and keyinformation corresponding to each slot may be filled in any order. Forexample, a “departure place slot”, a “destination slot”, and a “timeslot” are set in the first task engine, and the key informationcorresponding to each slot may be successively filled in an order of the“departure place slot”, the “destination slot”, and the “time slot”.Alternatively, the key information corresponding to each slot may besuccessively filled in an order of the “time slot”, the “destinationslot”, and the “departure place slot”.

In another example of this application, a plurality of slots may be setin the first task engine, and each slot has a different priority. Keyinformation corresponding to each slot may be filled according topriorities of the slots. For example, an air ticket booking task engineincludes three slots, which are respectively a “departure place slot”, a“destination slot”, and a “time slot”. In addition, a priority of the“time slot” is set to be the highest, a priority of the “departure placeslot” is set to be the second highest, and a priority of the“destination slot” is set to be the lowest. In this case, keyinformation corresponding to the “time slot” may be first filled, keyinformation corresponding to the “departure place slot” is then filled,and key information corresponding to the “destination slot” is finallyfilled.

In this embodiment of this application, a process of filling the keyinformation corresponding to each slot is detailed using the first slotas an example. First, the key information corresponding to the firstslot is extracted from the request information entered by the user. Ifthe key information can be extracted, and the extracted key informationmeets the condition, filling of the first slot is completed. If the keyinformation fails to be extracted from the request information, or ifthe key information can be extracted, but the extracted key informationdoes not meet the condition, the target key information is obtained fromthe shared parameter list of the user, and the target key information isused as the key information corresponding to the first slot.

Optionally, the procedure shown in FIG. 3 may further include updating,by the server, the shared parameter list of the user based on a semanticidentification result of each task engine, where the semanticidentification result includes intention information and key informationthat meets the condition.

For example, if a first request entered by a user A is “booking an airticket from Beijing to Shanghai tomorrow”, a semantic identificationresult obtained by the air ticket booking task engine may be{intention=“air ticket booking”, time=“tomorrow”, departureplace=“Beijing”, and destination=“Shanghai”}. Intention information is{intention=“air ticket booking”}, and key information that meets thecondition is {time=“tomorrow”, departure place=“Beijing”, anddestination=“Shanghai”}.

In this embodiment of this application, when the first requestinformation corresponds to not only the first task engine, but also Nother task engines, for example, the user enters first requestinformation of “booking a ticket from Beijing to Shanghai tomorrow”, thecentral control module of the human-computer interaction system performsintention identification on the first request information entered by theuser, and finds that the first request information corresponds to“ticket booking”. However, the entire human-computer interaction systemincludes the “air ticket booking task engine”, a “train ticket bookingtask engine”, and a “bus ticket booking task engine”. In this case, thecentral control module may separately send the first request informationto the “train ticket booking task engine”, the “bus ticket booking taskengine”, and the “air ticket booking task engine”. The first requestinformation may be referred to as corresponding to the foregoing threetask engines the “train ticket booking task engine”, the “bus ticketbooking task engine”, and the “air ticket booking task engine”.

In this embodiment of this application, when the first task requestcorresponds to N+1 task engines, and the N+1 task engines include thefirst task engine and the foregoing other N task engines, the N+1 taskengines may send semantic identification results of the N+1 task enginesfor the first request information to the central control module, and thecentral control module may select, from the N+1 semantic identificationresults, a semantic identification result that meets a rule, forexample, an optimal semantic identification result, to update the sharedparameter list of the user.

As shown in FIG. 4A and FIG. 4B, in an example of this application, anexample in which the foregoing server shown in FIG. 3 includes a centralcontrol module, a task engine module, and a multi-task parameter sharingmanagement module is used to detail the information processing procedureshown in FIG. 3.

Step S401. An intelligent terminal receives first request informationentered by a user, and sends the first request information to thecentral control module of a human-computer interaction system.

Step S402. The central control module performs intention identificationon the first request information, obtains one or more task enginesrelated to the first request information, and sends the first requestinformation to the one or more task engines in the task engine module.

Step S403. A task engine determines a slot corresponding to the taskengine.

Different task engines may correspond to different slots. For example, aslot corresponding to an air ticket booking task engine may be a“departure place slot”, a “destination slot”, or a “place slot”. A slotcorresponding to a weather query task engine may be a “place slot” or a“time slot”.

Step S404. The task engine extracts key information from the firstrequest information based on the slot corresponding to the task engine.

For example, for the weather query task engine, slots corresponding tothe weather query task engine may include the “place slot” and the “timeslot”. The weather query task engine may successively extract, from thefirst request information entered by the user, key informationcorresponding to the “place slot” and the “time slot”. For anotherexample, the first request information entered by the user may be “queryweather conditions of Beijing tomorrow”, and the weather query taskengine may successively extract, from the foregoing first requestinformation, key information “Beijing” corresponding to the “place slot”and key information “tomorrow” corresponding to the “time slot”.

Step S405. For a slot, if key information can be extracted from thefirst request information, and the extracted key information meets acondition, step S409 is performed, otherwise, step S406 is performed.

Step S406. The task engine sends a read instruction to the multi-taskparameter sharing management module.

Step S407. The multi-task parameter sharing management module obtainstarget key information from a shared parameter list of the user.

Step S408. The multi-task parameter sharing management module sends thetarget key information to the task engine.

Step S409. The task engine obtains a semantic identification result forthe first request information.

The semantic identification result includes intention information forthe first request information and the key information that meets thecondition.

Step S410. The task engine sends the semantic identification result forthe first request information to the central control module.

Step S411. The central control module updates the shared parameter listof the user in the multi-task parameter sharing management module basedon the semantic identification result sent by the task engine.

It should be noted that in the foregoing procedure shown in FIG. 4A andFIG. 4B, an example in which the task engine module reads informationfrom the shared parameter list, and the central control module updatesthe shared parameter list is used for description. In this embodiment ofthis application, an entity for reading information from the sharedparameter list and an entity for updating the shared parameter list arenot limited. For example, in this application, the central controlmodule may be responsible for reading information from the sharedparameter list and updating the shared parameter list. Alternatively,the task engine module is responsible for reading information from theshared parameter list and updating the shared parameter list.Alternatively, the central control module is responsible for readinginformation from the shared parameter list, and the task engine moduleis responsible for updating the shared parameter list. Alternatively,the task engine module is responsible for reading information from theshared parameter list, and the central control module is responsible forupdating the shared parameter list.

This embodiment of this application gives a detailed description of “howto obtain the target key information based on the shared parameter listof the user” in the foregoing procedure shown in FIG. 3 or FIG. 4A andFIG. 4B.

This embodiment of this application provides two types of sharedparameter lists a first type of shared parameter list and a second typeof shared parameter list. The target key information may be obtainedusing the first type of shared parameter list or the second type ofshared parameter list.

The first type of shared parameter list is when there is one sharedparameter list, and all task engines in the human-computer interactionsystem share the shared parameter list, that is, the foregoingmulti-task parameter sharing management module stores only one sharedparameter list.

In an example of this application, for the first type of sharedparameter list, the first type of shared parameter list may include acorrespondence between the first task engine and one or more taskengines, a correspondence between slots included in any two task enginesthat have a correspondence, and a correspondence between a second slotand the target key information. The one or more task engines include thesecond task engine. For the first type of shared parameter list, thefollowing manner may be used to obtain the target key information.

The second task engine is determined based on the correspondence betweenthe first task engine and the one or more task engines.

Optionally, the second task engine may be configured to be responsiblefor second request information of the user, where the second requestinformation and the first request information may occur within a presettime, and the second request information and the first requestinformation occur within a preset quantity of dialogue rounds.

The second slot that has a correspondence with a first slot of the firsttask engine is determined, based on the correspondence between slots,from slots that are included in the second task engine and that areincluded in the shared parameter list.

The target key information is determined based on the correspondencebetween the second slot and the target key information.

In this example, three correspondences may be stored in the first typeof shared parameter list a correspondence between different taskengines, a correspondence between slots included in two task engineshaving a correspondence, and a correspondence between slots included ineach task engine and target key information.

For example, as shown in FIG. 1, a weather query task engine is used asan example, and a process of obtaining target key information may be asfollows. First, task engines that interact with the user within a presettime (for example, 10 minutes) and a preset quantity of dialogue rounds(for example, five rounds of dialogue, where a process of one round ofdialogue includes that the user enters a piece of request informationand the human-computer interaction system feeds back a piece ofinformation) are obtained. For example, the task engines that interactwith the user may include {an air ticket booking task engine, a takeawayordering task engine}. Then, task engines that have a correspondencewith the weather query task engine in the shared parameter list areobtained, and may be, for example, {the air ticket booking task engine,a train ticket booking task engine, a hotel reservation task engine}. Anintersection set of the two sets is obtained, that is, the intersectionset of {the air ticket booking task engine, the takeaway ordering taskengine} and {the air ticket booking task engine, the train ticketbooking task engine, the hotel reservation task engine} is obtained. Itcan be learned that the intersection set of the two is {the air ticketbooking task engine}. Then, in slots of the air ticket booking taskengine, a slot corresponding to a place slot of the weather query taskengine is searched for. It can be learned from FIG. 5 that the slotcorresponding to the place slot of the weather query task engine is adestination slot of the air ticket booking task engine. Finally, targetkey information corresponding to the destination slot, that is,Shanghai, is used as key information of the place slot of the weatherquery task engine.

In another example of this application, for the first type of sharedparameter list, the first type of shared parameter list may include acorrespondence between a second slot and target key information. For thefirst type of shared parameter list, the following manner may be used todetermine the target key information determining, using a contextparameter of the user, the second task engine that is adjacent to thefirst task engine in terms of time, where the second task engine isconfigured to be responsible for second request information of the user,a slot having the same type as the first slot is set in the second taskengine, and the adjacency of time means that an occurrence time of thesecond request information is adjacent to an occurrence time of thefirst request information, determining, from slots of the second taskengine, the second slot having the same type as the first slot, anddetermining the target key information based on the correspondencebetween the second slot and the target key information.

It should be noted that, in this example of this application, that thefirst task engine is adjacent to the second task engine in terms of timemay include the following two cases. In a first case, the first taskrequest for which the first task engine is responsible and the secondtask request for which the second task engine is responsible areadjacent in terms of time, in other words, the first task requestentered by the user is adjacent to the second task request in terms oftime. For example, the user first enters, in the human-computerinteraction system, the first task request of “booking an air ticketfrom Beijing to Shanghai”, and then enters, in the human-computerinteraction system, the second task request “How is the weather overthere”. It may be considered that the first task request and the secondtask request are adjacent in terms of time. In addition, it is set thatthe “air ticket booking” task engine is responsible for the “first taskrequest”, and the “weather query” task engine is responsible for the“second task request”, and in this case, it may be determined that the“air ticket booking” task engine is adjacent to the “weather query” taskengine in terms of time. In a second case, the first task request forwhich the first task engine is responsible and the second task requestfor which the second task engine is responsible are separated by apreset time in terms of time, and both are within a preset quantity ofdialogue rounds.

In this example, only one correspondence is stored in the entire sharedparameter list, that is, a correspondence between a slot of each taskengine and key information.

Filling of the place slot of the weather query task engine is still usedas an example for description. A process of obtaining the target keyinformation may be as follows. First, in the context parameter of theuser, a task engine adjacent to the weather query task engine isobtained, that is, a task engine that interacts with the user before theuser interacts with the weather query task engine. For example, as shownin FIG. 6, the task engine adjacent to the weather query task engine interms of time is an air ticket booking task engine. Then, slots of theair ticket booking task engine are searched for a slot with the sameslot type as the place slot. For example, the found slot with the sametype is a destination slot. Finally, key information, namely Shanghai,corresponding to the destination slot of the air ticket booking taskengine in the shared parameter list is used as key informationcorresponding to the place slot in a weather query field.

The second type of shared parameter list is when there are a pluralityof shared parameter lists, and each task engine exclusively occupies oneshared parameter list. For example, the entire human-computerinteraction system includes N task engines. In this case, the multi-taskparameter sharing management module may store N shared parameter lists,and each task engine in the N task engines exclusively occupies oneshared parameter list in the N shared parameter lists.

For the second type of shared parameter list, a correspondence between asecond slot and the target key information may be stored in the sharedparameter list. The target key information may be obtained in thefollowing specific manner obtaining the first task engine correspondingto the first request information, obtaining the second task engine,where the second task engine corresponds to a second vertical field, thefirst task engine corresponds to a first vertical field, a correlationbetween the first vertical field and the second vertical field isgreater than a preset threshold, and the correlation between the firstvertical field and the second vertical field is obtained by clusteringhistorical data, searching a shared parameter list exclusively occupiedby the second task engine for a slot that has the same slot type as thefirst slot, and using the slot as the second slot, and determining thetarget key information based on the correspondence between the secondslot and the target key information.

In an example of this application, for example, a shared parameter listmaintained by an air ticket booking task engine may be shown in FIG. 7.

In this embodiment of this application, the shared parameter list may begenerated based on a historical dialogue parameter between a user andthe human-computer interaction system. For example, the user entersrequest information of “booking an air ticket from Beijing to Shanghaitoday” to the human-computer interaction system. In this case, the airticket booking task engine may separately extract, from the requestinformation, key information “Beijing” corresponding to a “departureplace slot”, key information “Shanghai” corresponding to a “destinationslot”, and key information “today” corresponding to a “time slot”.Finally, the shared parameter list exclusively occupied by the airticket booking task engine is updated based on the key informationcorresponding to different slots.

In this embodiment of this application, the foregoing example is stillused. The user first enters, in the human-computer interaction system,the request information of “booking an air ticket from Beijing toShanghai today”, and the foregoing shared parameter list shown in FIG. 7is generated. Then the user enters request information “How is theweather over there” in the human-computer interaction system, and it canbe found that the request information should be handled by the weatherquery task engine. Then the weather query task engine may separatelyextract key information corresponding to the “place slot” and the “timeslot” from the request information entered by the user. It can be foundthat the key information “over there” extracted for the “place slot” isdemonstrative information, and the key information for the “time slot”fails to be extracted, that is, information is absent for the “timeslot”. In this embodiment of this application, it can be set thatneither “information absence” nor the “demonstrative information” meetsa condition. In this case, the following manner may be used to obtainthe target key information obtaining a first vertical fieldcorresponding to the weather query task engine, obtaining a secondvertical field whose correlation with the first vertical field isgreater than a preset threshold, where the correlation between the firstvertical field and the second vertical field may be obtained byclustering historical data, obtaining a second task engine correspondingto the second vertical field, and obtaining the target key informationfrom a shared parameter list exclusively occupied by the second taskengine.

In this application, the second task engine may be set as an air ticketbooking task engine. In this case, key information that meets acondition may be obtained in the foregoing shared parameter list shownin FIG. 7.

For example, in an example of this application, the shared parameterlist shown in FIG. 7 may be searched for the key information that meetsthe condition and that corresponds to the “place slot” in the weathertask engine. It may be learned from the FIG. 7 that “Shanghai” is thekey information that meets the condition and that corresponds to the“place slot” in the weather query task engine. Similarly, the sharedparameter list shown in FIG. 7 may be searched for the key informationcorresponding to the “time slot” of the weather task engine. It may belearned from the FIG. 7 that “today” is the key information that meetsthe condition and that corresponds to the “time slot” in the weatherquery task engine.

It may be learned from the foregoing analysis that the correspondencebetween the second slot and the target key information is stored in boththe first shared parameter list and the second shared parameter list. Inthis embodiment of this application, the key information correspondingto the second slot is unique and updatable.

In an example of this application, the key information corresponding tothe second slot may be updated in the following manner. The serverreceives third request information entered by the user, where the secondtask engine is responsible for the third request information, the serverextracts, from the third request information, key informationcorresponding to the second slot of the second task engine, the serverupdates, based on the key information corresponding to the second slotthat is extracted from the third request information, the target keyinformation corresponding to the second slot in the correspondencebetween the second slot and the target key information included in theshared parameter list.

For the first type of shared parameter list and the second type ofshared parameter list, as shown in FIG. 8A and FIG. 8B, this applicationprovides another information processing procedure, and the procedureincludes the following steps.

In the procedure shown in FIG. 8A and FIG. 8B, three rounds of dialoguebetween a user and a human-computer interaction system are used as anexample for detailed description.

The first round of dialogue is when the user enters request information“How is the weather in Beijing today” to the human-computer interactionsystem. The human-computer interaction system may perform intentionidentification on the request information entered by the user, anddetermine that the request information should be handled by the weatherquery task engine. For a place slot of the weather query task engine,key information “Beijing” may be extracted from the request information.For a time slot of the weather query task engine, key information“today” may be extracted from the request information. Finally, ahistorical parameter list is generated, as shown in Table 1.

TABLE 1 User identification (ID) Intention Time Place *** Weather queryToday Beijing

The second round of dialogue is when the user continues to enter requestinformation of “booking an air ticket from Beijing to Buenos Airestomorrow” to the human-computer interaction system. Similarly, thehuman-computer interaction system may perform intention identificationon the request information of the user, and determine that the requestinformation should be handled by an air ticket booking task engine.Then, the air ticket booking task engine may separately extract, fromthe request information, key information “Beijing” corresponding to a“departure place slot”, key information “Buenos Aires” corresponding toa “destination slot”, and key information “tomorrow” corresponding to atime slot. Finally, a historical parameter list is generated, as shownin Table 2.

TABLE 2 User ID Intention Departure place Destination Time *** Airticket booking Beijing Buenos Aires Tomorrow

In this embodiment of this application, the historical parameter listshown in Table 1 and the historical parameter list shown in Table 2 maybe stored in the first type of shared parameter list, or may be storedin the second type of shared parameter list. If the historical parameterlists are stored in the second type shared parameter list, thehistorical parameter list shown in Table 1 may be a shared parameterlist exclusively occupied by the weather query task engine, and thehistorical parameter list shown in Table 2 may be a shared parameterlist exclusively occupied by the air ticket booking task engine.

The third round of dialogue is when the user enters request information“How is the weather over there” to the human-computer interactionsystem.

Step S801. Receive request information “How is the weather over there”in the third round of dialogue entered by a user.

Step S802. Extract key information from the request information in thethird round of dialogue.

For the extracted key information, refer to Table 3.

TABLE 3 User ID Intention Time Place *** Weather query ? Over there

Step S803. Obtain a required information slot set L0={“time”, “place”}that is absent from a weather query scenario.

Optionally, after step S803, the method may further include step S804,step S805, step S806, and step S807.

Step S804. Determine whether a predefined rule exists in filling of theinformation slot, and if the predefined rule does not exist, step S805is performed, or if the predefined rule exists, step S808 is performed.

The predefined rule refers to whether a shared parameter list can beused to fill the information slot.

Step S805. Determine whether a sensor can be used to fill the keyinformation in the absent information slot, and if the sensor can beused, step S806 is performed, or if the sensor cannot be used, step S807is performed.

Step S806. Fill “location information” using the sensor.

Step S807. Prompt the user to enter the “location information”.

In this embodiment of this application, step S804 to step S807 is toprovide different manners of filling the information slot. For example,a shared parameter list manner may be used, a sensor manner may be used,or a manually entering manner by the user may be used.

In this embodiment of this application, alternatively, step S808 may bedirectly performed after step S803, that is, the key information of theinformation slot is directly filled in the shared parameter list manner.

Step S808. Determine, one by one according to a predefined rule, whetherthe slot of L0 is predefined to a value in a shared parameter listduring scenario development, and if the slot of L0 is predefined to avalue, a set L1={ “time”, “place”} is added.

Step S809. When L1 is not empty, a set L2={“place”, “time”} is obtainedbased on a priority of each slot in L1.

Step S810. Search the shared parameter list for a historical “location”parameter of the user based on a user ID.

Step S811. Determine whether there is a value for the historical“location” parameter, and if the value does not exist, step S812 isperformed, or if the value exists, step S813 is performed.

Step S812. Prompt the user to enter the “location” information.

Step S813. Fill the value of the historical “location” parameter in a“location” slot.

In this embodiment of this application, the “destination: Buenos Aires”shown in Table 2 may be filled in the “location” slot to generate keyinformation shown in Table 4.

TABLE 4 User ID Intention Time Place *** Weather query ? Buenos Aires

Step S814. Search the shared parameter list for a historical “time”parameter of the user based on the user ID.

Step S815. Determine whether there is a value for the historical “time”parameter, and if the value exists, perform step S816, or if the valuedoes not exist, perform step S817.

Step S816. Fill the value of the historical “time” parameter in a “time”slot.

In this embodiment of this application, the “time: Tomorrow” shown inTable 2 may be filled in the time slot to generate key information shownin Table 5.

TABLE 5 User ID Intention Time Place *** Weather query Tomorrow BuenosAires

Step S817. Prompt the user to enter “time” information.

In the foregoing manner, it may be learned that in this embodiment ofthis application, when the key information that meets the conditionfails to be extracted from the request information entered by the user,the historical dialogue parameter of the user can be used to obtain thekey information that meets the condition. In this way, the user does notneed to enter request information again, user experience is relativelygood, and human-computer interaction efficiency is relatively high.

Based on the same concept, as shown in FIG. 9, this application providesan information processing apparatus 900. The information processingapparatus 900 may be a terminal device, a server, or the like, andincludes a transceiver unit 901 and a processing unit 902.

The transceiver unit 901 is configured to receive first requestinformation entered by a user.

It should be noted that the transceiver unit 901 may be a hardwareapparatus such as a transceiver, or may be a logical unit such as a datainterface. This is not limited in this application.

The processing unit 902 is configured to perform intentionidentification on the first request information, and determine a firsttask engine responsible for the first request information, where a firstslot is set in the first task engine, extract key information from thefirst request information based on the first slot, and if the keyinformation fails to be extracted from the first request informationbased on the first slot, or if the key information is extracted from thefirst request information based on the first slot, but the extracted keyinformation does not meet a condition, obtain target key informationfrom a shared parameter list of the user.

The shared parameter list includes at least a correspondence between asecond slot and the target key information, the second slot and thefirst slot have a same slot type, the second slot is a slot in thesecond task engine, and the first task engine is different from thesecond task engine.

For specific descriptions of the transceiver unit 901 and the processingunit 902, refer to the description of the foregoing informationprocessing method shown in FIG. 3. Details are not described hereinagain.

Based on the same concept, as shown in FIG. 10, an embodiment of thisapplication further provides a structure of an information processingapparatus 100. The information processing apparatus 100 may be aterminal device or a server. Optionally, the information processingapparatus 100 may be a central control module in the server, or afunction of the information processing apparatus 100 is implemented bythe central control module in the server. Further, optionally, theinformation processing apparatus 100 may be a central control module inthe terminal device, or a function of the information processingapparatus 100 is implemented by the central control module in theterminal device. As shown in FIG. 10, the information processingapparatus 100 may include a communications interface 101 and a processor102. The information processing apparatus 100 may further include amemory 103. The memory 103 may be set inside the information processingapparatus 100, or may be set outside the information processingapparatus. The processing unit 902 shown in FIG. 9 may be implemented bythe processor 102. The transceiver unit 901 may be implemented by thecommunications interface 101. The processor 102 receives service datausing the communications interface 101.

In this embodiment of this application, the communications interface 101may be a circuit, a bus, a transceiver, or any other apparatus that canbe configured to perform information exchange.

In this embodiment of this application, the processor 102 may be ageneral purpose processor, a digital signal processor, anapplication-specific integrated circuit, a field programmable gate arrayor another programmable logic device, a discrete gate or transistorlogic device, or a discrete hardware component, and may implement orperform the information processing method that is shown in FIG. 3, FIG.4A and FIG. 4B, or FIG. 8A and FIG. 8B and that is disclosed in theembodiments of this application. The general purpose processor may be amicroprocessor or any conventional processor or the like. The steps ofthe method disclosed with reference to the embodiments of thisapplication may be directly performed by a hardware processor, or may beperformed using a combination of hardware in the processor and asoftware unit. Program code used by the processor 102 to implement theforegoing method may be stored in the memory 103. The memory 103 iscoupled to the processor 102. The processor 102 may operate incooperation with the memory 103. The memory 103 may be a non-volatilememory such as a hard disk drive (HDD) or a solid-state drive (SSD), ormay be a volatile memory such as a random-access memory (RAM). Thememory 103 is any other medium capable of carrying or storing expectedprogram code in a form of an instruction or a data structure and capableof being accessed by a computer. However, this is not limited thereto.

In this embodiment of this application, a specific connection mediumbetween the communications interface 101, the processor 102, and thememory 103 is not limited. In this embodiment of this application, thememory 103, the processor 102, and the communications interface 101 areconnected by a bus in FIG. 10. In FIG. 10, the bus is indicated by athick line. The foregoing is merely an example for description. Mannersof a connection between other components are not limited thereto. Thebus may be classified into an address bus, a data bus, a control bus,and the like. For ease of representation, only one thick line is used torepresent the bus in FIG. 10, but this does not mean that there is onlyone bus or only one type of bus.

Based on the foregoing embodiments, an embodiment of this applicationfurther provides a computer storage medium. The storage medium stores asoftware program, and when being read and executed by one or moreprocessors, the software program can implement the method provided inany one or more of the foregoing embodiments. The computer storagemedium may include any medium that can store program code, such as aUniversal Serial Bus (USB) flash drive, a removable hard disk, aread-only memory, a random access memory, a magnetic disk, or an opticaldisc.

Based on the foregoing embodiments, this application provides a computerprogram, where the computer program includes a computer instruction, andwhen the computer instruction is executed by a computer, the computer isenabled to perform the method provided in any one or more of theforegoing embodiments.

A person skilled in the art should understand that the embodiments ofthis application may be provided as a method, a system, or a computerprogram product. Therefore, this application may use a form of hardwareonly embodiments, software only embodiments, or embodiments with acombination of software and hardware. Moreover, this application may usea form of a computer program product that is implemented on one or morecomputer-usable storage media (including but not limited to a diskmemory, a compact disc read-only memory (CD-ROM), and an optical memory)that include computer-usable program code.

This application is described with reference to the flowcharts and/orblock diagrams of the method, the device (system), and the computerprogram product according to this application. It should be understoodthat computer program instructions may be used to implement each processand/or each block in the flowcharts and/or the block diagrams and acombination of a process and/or a block in the flowcharts and/or theblock diagrams. These computer program instructions may be provided fora general-purpose computer, a special-purpose computer, an embeddedprocessor, or a processor of any other programmable data processingdevice to generate a machine such that the instructions executed by acomputer or a processor of any other programmable data processing devicegenerate an apparatus for implementing a specific function in one ormore processes in the flowcharts and/or in one or more blocks in theblock diagrams.

These computer program instructions may be stored in a computer readablememory that can instruct the computer or any other programmable dataprocessing device to work in a specific manner such that theinstructions stored in the computer readable memory generate an artifactthat includes an instruction apparatus. The instruction apparatusimplements a specific function in one or more processes in theflowcharts and/or in one or more blocks in the block diagrams.

These computer program instructions may be loaded onto a computer oranother programmable data processing device such that a series ofoperations and steps are performed on the computer or the otherprogrammable device, thereby generating computer-implemented processing.Therefore, the instructions executed on the computer or the otherprogrammable device provides steps for implementing a specific functionin one or more processes in the flowcharts and/or in one or more blocksin the block diagrams.

Apparently, a person skilled in the art can make various modificationsand variations to this application without departing from the scope ofthis application. This application is intended to cover thesemodifications and variations of this application provided that they fallwithin the scope of protection defined by the following claims and theirequivalent technologies.

What is claimed is:
 1. An information processing method, comprising:receiving first request information from a user; determining a firsttask engine for the first request information, wherein a first slot isset in the first task engine; and obtaining target key information froma shared parameter list of the user when key information is notextracted from the first request information based on the first slot orwhen the key information is extracted from the first request informationbased on the first slot and the key information does not meet acondition, wherein the shared parameter list comprises a firstcorrespondence between a second slot and the target key information,wherein the second slot and the first slot have a same slot type,wherein the second slot is in a second task engine, and wherein thefirst task engine is different from the second task engine.
 2. Theinformation processing method of claim 1, wherein the shared parameterlist further comprises a second correspondence between the first taskengine and one or more task engines and a third correspondence betweenslots comprised in any two corresponding task engines, wherein the oneor more task engines comprise the second task engine, wherein theinformation processing method further comprises: determining the secondtask engine based on the second correspondence; determining the secondslot comprising a fourth correspondence with the first slot of the firsttask engine based on the third correspondence and from slots that are inthe second task engine and the shared parameter list; and determiningthe target key information based on the first correspondence.
 3. Theinformation processing method of claim 1, further comprising receivingsecond request information from the user, wherein the second task engineis configured for second request information, and wherein the secondrequest information and the first request information occur within apreset time.
 4. The information processing method of claim 1, whereinobtaining the target key information from the shared parameter list ofthe user comprises: determining the second task engine using a contextparameter of the user, wherein the second task engine is configured forsecond request information of the user, wherein the second task enginecomprises a third slot having the same slot type as the first slot, andwherein an occurrence time of the second request information is adjacentto an occurrence time of the first request information; determining thesecond slot has the same slot type as the first slot based on slots ofthe second task engine; and determining the target key information basedon the first correspondence.
 5. The information processing method ofclaim 1, wherein the shared parameter list is a shared parameter listexclusively occupied by the second task engine, wherein obtaining thetarget key information from the shared parameter list comprises:determining the second task engine based on a correlation between thefirst task engine and the second task engine, wherein the correlationbetween the first task engine and the second task engine is greater thana preset threshold; determining the shared parameter list exclusivelyoccupied by the second task engine based on the second task engine;searching the shared parameter list for a fourth slot that has the sameslot type as the first slot; using the fourth slot as the second slot;and determining the target key information based on the firstcorrespondence.
 6. The information processing method of claim 1, whereinthe key information that does not meet the condition comprisesdemonstrative information.
 7. The information processing method of claim1, wherein the target key information of the second slot is unique. 8.The information processing method of claim 1, further comprising:receiving third request information from the user, wherein the secondtask engine is configured for the third request information; extractingkey information of the second slot of the second task engine from thethird request information; and updating the target key information ofthe second slot in the first correspondence comprised in the sharedparameter list based on the key information of the second slot.
 9. Theinformation processing method of claim 1, wherein before extracting thekey information from the first request information, the informationprocessing method further comprises: determining a plurality of slotsset in the first task engine, wherein the slots have priorityinformation; and determining the first slot based on the priorityinformation.
 10. The information processing method of claim 1, whereinthe slot type comprises time, place, behavior, or character.
 11. Aninformation processing apparatus, comprising: a transceiver configuredto receive first request information from a user; and a processorcoupled to the transceiver and configured to: determine a first taskengine for the first request information, wherein a first slot is set inthe first task engine; and obtain target key information from a sharedparameter list of the user when the key information is not extractedfrom the first request information based on the first slot or when thekey information is extracted from the first request information based onthe first slot and the extracted key information does not meet acondition, wherein the shared parameter list comprises at least a firstcorrespondence between a second slot and the target key information,wherein the second slot and the first slot have a same slot type,wherein the second slot is a slot in a second task engine, and whereinthe first task engine is different from the second task engine.
 12. Theinformation processing apparatus of claim 11, wherein the sharedparameter list further comprises a second correspondence between thefirst task engine and one or more task engines and a thirdcorrespondence between slots comprised in any two corresponding taskengines, wherein the one or more task engines comprise the second taskengine, wherein the processor is further configured to: determine thesecond task engine based on the second correspondence; determine thesecond slot comprising a fourth correspondence with the first slot ofthe first task engine based on the third correspondence and from slotsthat are in the second task engine and the shared parameter list; anddetermine the target key information based on the first correspondence.13. The information processing apparatus of claim 11, wherein theprocessor is further configured to receive second request informationfrom the user, wherein the second task engine is configured for secondrequest information, and wherein the second request information and thefirst request information occur within a preset time.
 14. Theinformation processing apparatus of claim 11, wherein the processor isfurther configured to: determine the second task engine using a contextparameter of the user, wherein the second task engine is configured forsecond request information of the user, wherein the second task enginecomprises a third slot having the same slot type as the first slot, andwherein an occurrence time of the second request information is adjacentto an occurrence time of the first request information; determine thesecond slot has the same slot type as the first slot from slots of thesecond task engine; and determine the target key information based onthe first correspondence.
 15. The information processing apparatus ofclaim 11, wherein the shared parameter list is a shared parameter listexclusively occupied by the second task engine, wherein when obtainingthe target key information from the shared parameter list of the user,the processor is configured to: determine the second task engine basedon a correlation between the first task engine and the second taskengine, wherein the correlation between the first task engine and thesecond task engine is greater than a preset threshold; determine theshared parameter list exclusively occupied by the second task enginebased on the second task engine; search the shared parameter list for afourth slot that has the same slot type as the first slot; use thefourth slot as the second slot; and determine the target key informationbased on the first correspondence.
 16. The information processingapparatus of claim 11, wherein the key information that does not meetthe condition comprises demonstrative information.
 17. The informationprocessing apparatus of claim 11, wherein the target key information ofthe second slot is unique.
 18. The information processing apparatus ofclaim 11, wherein the transceiver is further configured to: receivethird request information from the user, wherein the second task engineis configured for the third request information, wherein the processoris further configured to: extract key information of the second slot ofthe second task engine from the third request information; and updatethe target key information of the second slot in the firstcorrespondence comprised in the shared parameter list based on the keyinformation of the second slot.
 19. The information processing apparatusof claim 11, wherein the processor is further configured to: determine aplurality of slots set in the first task engine, wherein the slots havepriority information; and determine the first slot based on the priorityinformation.
 20. A computer program product comprisingcomputer-executable instructions for storage on a non-transitorycomputer-readable medium that, when executed by a processor, cause aninformation processing apparatus to: receive first request informationfrom a user; determine a first task engine for the first requestinformation, wherein a first slot is set in the first task engine;obtain target key information from a shared parameter list of the userwhen the key information is not extracted from the first requestinformation based on the first slot or when the key information isextracted from the first request information based on the first slot andthe key information does not meet a condition, wherein the sharedparameter list comprises at least a first correspondence between asecond slot and the target key information, wherein the second slot andthe first slot have a same slot type, wherein the second slot is in asecond task engine, and wherein the first task engine is different fromthe second task engine.